OpenEdge Application Server:<br />Administration ASBMAN

Release 10.1A: OpenEdge Application Server:
Administration

ASBMAN

Starts, stops, adds AppServer agents, trims AppServer agents, and queries the status for an AppServer instance and its AppServer agent.

Syntax
Operating system

Syntax
UNIX

Windows
asbman {
  { -name AppServer-name 
    { -kill | -start | -stop | -query |
      -addservers number-to-start |
      -trimservers number-to-trim }
    [ -host host-name -user user-name | -user user-name ]
    [ -port port-number ]
  } | -help } 
-name AppServer-name
This parameter is required. It specifies the name of an AppServer.
-kill
Stops and removes the AppServer from memory, no matter what it is doing.
-start
Starts an AppServer.
-stop
Tells the NameServer to stop itself.
Note: The AppServer stops only after completing any active client requests.
-query
Queries an AppServer for its status.
-addservers number-to-start
Specifies the number of additional servers to start.
-trimservers number-to-trim
Specifies the number of additional servers to trim.
-host host-name
Specifies the name of the machine where the AdminServer is running. If a host name is not specified, it defaults to the local host name.
-user user-name
Specifies a user name and prompts for a password. A user name and password are required only when you use the -host parameter and specify a remote host name. If you specify a remote host name with the -host parameter but do not specify a user name with the -user parameter, you receive a prompt for a user name and password.

Windows supports three different formats for user-name:

A user name as a simple text string, such as “mary”, implies a local user whose user account is defined on the local Windows server machine, which is the same machine that runs the AdminServer.

A user name as an explicit local user name, in which the user account is defined on the same machine that runs the AdminServer, except the user name explicitly references the local machine domain, for example “.\mary”.

A user name as a user account on a specific Windows domain. The general format is Domain\User, in which the User is a valid user account defined within the domain and the Domain is any valid Windows Server, including the one where the AdminServer is running.

-port port-number
Specifies the port number of the machine on which the AdminServer is running. If a port number is not specified, it defaults to 20931.
-help
Displays command-line help.
Examples

Table B–2 shows several examples that use the ASBMAN command. Assume the AppServer instance is AS1 and the NameServer is NS1.
Table B–2: ASBMAN command examples
Task

Command
Start a local AppServer instance after starting the local controlling NameServer.
nsman -name NS1 -start 
asbman -name AS1 -start 
Start a remote AppServer instance after starting a remote controlling NameServer.¹
nsman -name NS1 -host nsserve -port 
20950 -user daniel -start 
asbman -name AS1 -host asserve -port 
20950 -user daniel -start 
Stop a local AppServer instance (AS1) and its controlling NameServer instance (NS1).
asbman -name AS1 -stop 
nsman -name NS1 -stop  
¹The AppServer and controlling NameServer are on different hosts and happen to use the same TCP/IP port number to access the AdminServer on each host. If you specify a host, the Progress Explorer always prompts for a user name (if necessary) and password. In this example, the commands specify the user name and prompt only for the password.

Task	Command
Start a local AppServer instance after starting the local controlling NameServer.	nsman -name NS1 -start asbman -name AS1 -start
Start a remote AppServer instance after starting a remote controlling NameServer.¹	nsman -name NS1 -host nsserve -port 20950 -user daniel -start asbman -name AS1 -host asserve -port 20950 -user daniel -start
Stop a local AppServer instance (`AS1`) and its controlling NameServer instance (`NS1`).	asbman -name AS1 -stop nsman -name NS1 -stop